| Buff |  | 23 CHF / 18 euros |
| Black polo |  | 31 CHF / 25 euros |
| Rugby polo |  | 50 CHF / 40 euros |
| Mousepad |
 | 13 CHF / 10 euros |
git clone git://git.mraw.org/ipc-gimpfu).
More on the reasons why I needed this module and those Gimp filters in
a later post.
In no particular order, here are my 4 picks for the DPL thunderdome:
Here it is.
Debian had seven hundred thousand bugs reported in its history.
Yet another French winner, indeed two, this time:
Here it is.
Debian had seven hundred thousand bugs reported in its history.
Yet another French winner, indeed two, this time:
KiBi is my hero
of the day. I ve long wondered why I couldn t select fixed-misc
as font on my workstation at the dayjob, which is running Kubuntu
Hardon Heroin. (Luckily, I managed to avoid upgrading to Prolonged Pain.)
Now I guess that ll work again.
My work laptop (running testing) also has got this X.org thingy. My keyboard
layout now has got a grml branch (named after the person
who first cursed about the insane idea of those toy-breaking boys to
rearrange the keycodes) that works with it. Since Debian is marginally
more sane than Kubuntu, in contrast to the gnu branch I use
on my orkstation, the grml branch still has Meta on the left
Alt key, not Mode_switch, as it still works in uxterm, which reduces
the diff between the MAIN branch (HEAD) on XFree86
and this beast.
And finally: X.org defaults to a black screen and disabled mouse pointer until an application first requests it. Totally unacceptable for evilwm(1) users, and letting people think it crashed, to boot. The Arch Linux guys found this, among others; the fix is: startx(1) users edit /etc/X11/xinit/xserverrc to add -retro behind the X, or copy the file to ~/.xserverrc and change it there:
#!/bin/sh exec /usr/bin/X -retro -nolisten tcp "$@"
For display managers,similar files exist in /etc/kde4/kdm and related places.
Thanks to the nice
Debian Swiss Knives
initiative!
Fixing software
Besides trying to maintain the whole X stack as usual, and preparing
the funky
wayland,
mesa,
and
weston
trio for experimental, I got myself into other areas.
Debugging gzip
Jakup Wilk noticed
a while ago that some multiarchified packages couldn t be co-installed
due to gzipped files being different between architectures. That was
reported as #647522 against the
gzip package.
While some developers consider the lack of determinism (as in: it s
not in the gzip specification, and the current implementation
generates different packages anyway!) as a dead-end for the multiarch
experiment, it didn t look like undebuggable or unfixable. And indeed,
as confirmed by a
quick
analysis:
a lack of clean-up when several files are processed at once can lead
to different results, depending on the order in which files are specified
on the command line; the patch for that is trivial, and was later
made smaller
and the need for it was
explained.
Working in the Release Team
I reviewed/approved a few packages for squeeze, but also took care
of handling or finishing a few transitions (as seen in my
hints file), among
which the funny iceweasel9/libmozjs ones; release tools are nice,
but one gets to learn lots of stuff at once (which isn t a negative
aspect). I hacked a tiny
collision detector
so that packages involved in several transitions can be easily
spotted. Given the huge number of ongoing transitions we had lately,
that didn t look overkill.
Squashing bugs
It had been a very long time since my last working on totally random
RC bugs. The Bug Squashing Party organized at
IRILL was a very nice opportunity to get back
to totally crazy bugs in unknown packages, but also to meet with other
Debian contributors; sponsoring maintainers with good patches on their
first try was nice, but walking other contributors through their first
patches sent to the BTS or through their first NMUs was nice too.
Waving good bye to yada
Back in the M rida QA meeting I attended in 2007, there were already
jokes about how bad yada was, and how it should die in a fire
etc. When I started looking at the RC bug list, I quickly switched to
scrolling it backwards, and I wondered how much work was left. The
details can be seen in #660548, and
the result is:
yada is gone!
sanity++;
packages.debian.org
Both long descriptions and translations for packages in some suites
disappeared after the
switch to Description-md5. Thanks
to a quick and reduced packages.debian.org setup (mostly: en+de
for squeeze+sid+experimental), I managed to find my way through
Perl and DB files to propose patches for
#657557. I m still waiting for a
confirmation, but in case it works fine, we could even get a fix for
DDTP/DDTSS.
mksh R40b (nowadays with filled
in user s caveats (for R40, too!)
and packager s upgrade hints) has
just been released. This is a should-have upgrade, fixing a number of
admittedly some obscure bugs, changing things begun in R40, improving
upon others. Thanks to the PLD Linux guys for spotting all these errors;
thanks to them and phpnet.org both for adopting mksh so well.
I have also fixed a bug in nroff(1) which will lead to an even
nicer looking HTML manpage mksh(1) (after the next rebuild and upload of
a MirBSD snapshot scheduled RSN).
jupp 3.1.16 took on the task
of merging Debian joe changes (aiming at an upload). I also split the
jupprc file into three versions (2.8 generic/DOS, 3.1+jupp and 3.7/Unix)
because of the differences in the baseline executables making rc files
partially mutually incompatible (think Insert key), annoyingly warning
(think syntax, hmsg), or less usable (joe s new menu system).
jupp 2.8.2 is a companion to
jupp 3.1.16 mostly because of the new help window character map
Binaries for jupp should be updated RSN too.
Considering Banja Luka is arriving quickly, the r in RSN should be
taken with a few grains of salt. I ve also scheduled working on the pcc
Debian package for the next future; updating lynx and maybe others like
OpenSSH in MirBSD is also due; cvs(1) will receive more of my time, but
before the next Upload I d like to fix LP#12230 once verified.
Builds for Debian/m68k are also still running. I note I did in fact
not manage to make a new base image, yet (but 2.6.39 kernels
miss a patch, anyway, so waiting for 3.0 is ok). It s still using gcc-4.4
because nobody tests gcc-4.6 and gcj-4.6 FTBFS due to SIGSEGV, but that s
ok in my books. rsyslog is broken but sysklogd works.
The #ksh Freenode page finally
got a well-deserved link to Planet Commandline. Throw more my way!
Acronyms and translations,
too. (Got Norwegian and Rumanian covered in the meantime. No idea whether any
RTL languages will work in that beast. But I m young and need the money)
Since I m writing a wlog entry anyway let me thank Gunnar for a nice
summary on the current Free Culture discussion; my comments on Nina s site
seem to be eaten, but let me support it fully, although, of course, I normally
use a copycenter style licence, which
is specifically written for general works of authorship under copyright law,
not limited to software. I did in fact have that in mind. Maybe some people
will like it (it s less than one Kibibyte long) either generally or just for
their everyday random musings (they can then keep CC-BY-SA for the big works
if they so desire).
Wouter, grass background makes green headlines illegible. I ve never liked,
and never installed manually, cups either. (Benny tells me that Apple s new
version refuses to talk with a non-Apple cups, kinda defeating the whole idea
I think.) Port 9100 is JetDirect (probably with an HP in front and some subset
of trailing) and just nice. (Being able to talk ESC/P with your printer
like print '\033K\x07\0\x3E\x81\x99\xA5\xA5\x81\x3E' >/dev/lpa too
rocks though, IMHO. Yes, mine can, and I still can. /dev/lpa is BSD.)
Kai, thanks for your vimrc lines:
:highlight TrailWhitespace ctermbg=red guibg=red :match TrailWhitespace /\s\+$\ \+\ze\t/
Automatic removal is harmful, though I just fell into the trap since jupprc contains needed whitespace at EOL but manual removal (bound to ^K] in jupp) rocks. And I like that your solution uses such strong a colour vim users are the single most represented offender group for actually leaving the redundant whitespace at EOL there, and it should hurt their eyes. (Sadly there is some vehement disagreement preventing them from inclusion in grml-etc-core but that s why I re-post them here.) Ah, and jupp can of course display whitespace visibly (although it uses / , replacing the arrow with if no UTF-8, not ), accessible with ^Ov. Steve, want to put up a checklist for sites? We can crowdsource the testing to maybe get some interesting results Some other people would get more comments if they were idling in IRC (Freenode) or allow comments on their blog, specifically without too high an entrance barrier OpenID is ok, but many other things, and ECMAscript, are not; but I can t really say that loud because our wlog is static HTML compiled from a flat plaintext data source so it doesn t allow such either. I often forget what I wanted to add if I can t get it out quickly enough (especially at work). Sowwy Me like the cat picture postings (Amayita, Tiago, Gracias!).
The file properties will show the file size in base10 and base2:
PS: I failed to launch nautilus in English. Therefore the screen shots are in German.
PS : You can grab the modified nautilus package for Ubuntu 10.10 (maverick) from my experimental PPA (at your own risk!).
man 5 byteprefix once installed. Thanks to Stefano Rivera for writing the man page!
For a demonstration how this library used by an application can look like, read my previous post.
ikiwiki and my nickname s
KiBi, ikibiki.org sounded fun, so I picked that one.
Now, it s a bit long to type, error-prone (how many times did I type
ikiwiki instead ), and even my family has troubles remembering it.
Other kibi.* domain names weren t released in the meanwhile, so
looking into stuff I care about, something cat-related could do the
job. And since I ve been using
mraw in my signature for a while, I picked
that one. So my blog lives at http://blog.mraw.org/ now. The old
domain name will be kept for a while though.
This is the tenth Debian XSF News issue. It is basically meant to be
a follow-up to DXN#9.
xkb-data (a.k.a. xkeyboard-config)
side, as
explained by Sergey Udaltsov.
Protocol:
experimental was a bit overcautious, so upload again unstable.experimental for a while, changes were announced to debian-boot@ unstable.libx11-6; also announced to debian-boot@ experimental.unstable.udebs for generic
drivers for non-Linux architectures. I cleaned them up a bit
(especially on the vesa side, getting rid of libdrm entirely),
got them test-built on a kfreebsd-amd64 box, while Samuel
Thibault was doing the same on a hurd-i386 box. I
raised the topic
on debian-boot@, debian-bsd@, and debian-hurd@, mentioning
the remaining steps.
Drivers (all accepted by ftpmasters after a tiny trip to the NEW queue):
experimental.experimental.experimental.x11-xserver-utils: Julien did everything for DSA-2213 unstable, squeeze-security, lenny-security.experimental.testing (from now on I ll
use testing instead of wheezy so that it s clear it s about
week after week migrations to the testing distribution, rather
than our final plans for the next stable release). After a while,
and thanks to
some hand-holding
from our nice release managers (hi, Adam!), linux-2.6,
libdrm, mesa, xorg-server, and several dozen drivers migrated
to testing. Yay!experimental previously) unstable.unstable and 7.10.1 in experimental (see above) unstable.experimental and supersedes 0.21.4 unstable.unstable.unstable.ati driver unstable. As already
blogged by Riku,
getting replaced by script is really great!
Until now, I ve had a crontab fetching my supporting-very-big-mails
(up to 100MB or so) mailbox every few minutes, and looking into my
=incoming-buildd/ maildir on a very regular fashion. With some
simple mutt maildir hooks, replying to a Successful log would
trigger extracting the changes file from there, setting some
options, like PGP inline signing, and the mail would be ready to go
back to the buildd. That part was just about being a GPG-signing
monkey, so really not a funny part.
Since we no longer have to worry about this boring and time-consuming
task, I ve switched to a crontab firing up 4 times a day, and I try to
deal with all incoming mails at once. Coupled with the new filters
(e.g. on out-of-date packages on the buildd status page), I started using my time to file
FTBFS bugs again, so that maintainers notice their packages fail to
build without having to wait for a non-happening testing migration.
After 10 days, the following mutt filter in =debian-bts/ lists
69 bugs:
~s "Bug#.*FTBFS" ~P ~d 01/04/2011-
Subject contains Bug#.*FTBFS, mails from me, starting from 01/04/2011.)
Figuring out whether that s due to another package s bug, an outdated
chroot, a temporary glitch, etc. might take some time; that s why it s
a bit hard to stay on top of things; and when the backlog grows up,
motivation to go through this tedious task can be pretty low,
especially when one sees repeated mistakes. I hope the amount of
(possible) use cases for #620686 will
decrease over time; instead, I d be very happy if maintainers could at
least check what s mentioned in configure.ac/configure.in. Keeping
an eye on its diff between upstream versions should be easy
enough. ;)
This is the ninth Debian XSF News issue. As can be seen below, I m
not yet decided how to present various items. This time, I ll try to
gather all updated packages since the previous issue, grouped by
category, with a single line summary. Lengthy comments come after that
list of updated packages.
experimental.unstable.unstable.experimental.testing if the Linux kernel migrates some day unstable.experimental.unstable.unstable version against experimental s server experimental.experimental.experimental.unstable.unstable wkhtmltopdf failed on several buildds, so I disabled PDF generation, and completed the switch to asciidoc mentioned in DXN#8 unstable.unstable.unstable.experimental only? Because bad regressions happen, on a regular
basis; so it seems quite nice to keep well-tested versions in
unstable for now. Once the X stack has migrated to testing
(which as explained in DXN#7 and
DXN#8 is waiting for the Linux kernel to
migrate), new versions in unstable are welcome, so that one can
tell easily whether bugs with those versions are regressions from
the versions available in testing. In the meanwhile, one can build
packages from the git repositories, using the debian-unstable
branch (which is the default).unstable as
they are released? First of all, our waiting for the kernel means
we have no issues on the 10-day delay front. Second of all, input
bugs are usually fixed very quickly upstream (you can go there and
thank Peter Hutterer in particular). So staying very close to
whatever upstream ships makes some sense. Mandatory warning: What follows is for testing only, and
insecure (root all over the place, giving access to host devices
from the container, etc.).
Problem of the day
mesa needs to be rebuilt against the
library. Doing so on a system running stable doesn t seem too
good: some newer libraries might be needed; and using make
install could make it harder to remember additional bits installed
all over the place ($DESTDIR is our friend but that might mean
more work on the build system side to get everything
detected).squeeze system.apt-get install lxc, read its README.Debian, get the mount
point set up./usr/lib/lxc/templates/lxc-debian template somewhere as
lxc-squeeze, and edit it:
dhcp-client with dhcp3-client.lenny with squeeze.ftp.debian.org.lxc-test directory, and create a container:
./lxc-squeeze -p lxc-test.lxc-start -n
test -f lxc-test/config (the test name passed through -n can
be used to call lxc-stop -n test). Use root/root to get in./etc/apt/sources.list to point to sid instead, and
dist-upgrade (using squeeze to start with means fewer headaches
while bootstrapping, in case sid breaks or gets into some
transition).lxc-stop and lxc-start to make sure the container can be
stopped and restarted at will.udev + LXC =
fail. So let s install it, note that it can t be configured, edit
/var/lib/dpkg/info/udev.postinst, add exit 0 at the top, and
dpkg --configure udev./dev. Using mknod would be
too easy, that s called a container for a reason. So let s edit
the config file (the one passed to lxc-start earlier) to add a
few devices (see below for an example).lxc-stop/lxc-start) the container,
mknod on those devices is now possible.crw-rw---- 1 root video 226, 0 Apr 5 02:34 /dev/dri/card0
crw-rw---- 1 root video 29, 0 Apr 5 02:34 /dev/fb0
crw------- 1 root root 4, 7 Apr 5 02:34 /dev/tty7
crw------- 1 root root 4, 8 Apr 5 02:34 /dev/tty8
config file accordingly, adding those lines (watch the syntax,
it doesn t like extra whitespaces):
lxc.cgroup.devices.allow = c 226:0 rwm
lxc.cgroup.devices.allow = c 29:0 rwm
lxc.cgroup.devices.allow = c 4:7 rwm
lxc.cgroup.devices.allow = c 4:8 rwm
cd /dev
mkdir -p dri
mknod -m 666 dri/card0 c 226 0
mknod -m 666 fb0 c 29 0
mknod -m 666 tty7 c 4 7
mknod -m 666 tty8 c 4 8
apt-get install xorgstartxstrace -f can help diagnose issues. If /dev/dri/card0 shows up
with ENODEV, an old libdrm could even remove that device, so
running mknod is needed again (but not sufficient)startx from the
container again should give better results (that s what happened
here).startx just works , just use ^Z then bg to put it in the
background.awesome)
and mesa-utils, and enjoy!export DISPLAY=:0
awesome &
# this is not a benchmark:
glxgears &
# direct rendering:
glxinfo egrep '(direct renderer)'
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on ATI RS690
XFS) issue as
reported upstream in
FDO#31501
or in Debian as #616578. The
easy fix is to get rid of FontPath in xorg.conf, or to remove
the xfs package. It s deprecated anyway.libxt to find
the
guilty commit
was quite easy. After a quick upload with this commit reverted, a
real fix
was pushed upstream; a new upstream was released, packaged, and
uploaded right after that.upowerd s polling every 30 seconds:
#613745.6.0.1 squeeze point release, leading to cursor
issues with Intel graphics:
#618665.CurrentProblemsInUnstable page on the wiki, which is long
unmaintained (and that s why I m not linking to it). I m not
exactly sure what to do at this point, but I think having a similar
page on http://pkg-xorg.alioth.debian.org/, linked from the
how to report bugs
page would make sense. Common issues as well as their solutions or
workarounds for stable should probably go to the FAQ
instead.wheezy. The 2.6.38 upstream release was
quickly
pushed to unstable,
which is great news, even if it s not really ready yet (since it s
still failing to build on armel and mips).lenny-backports was quickly installed and the website should
look fine.wkhtmltopdf (WebKit-based HTML
to PDF converter), since the table of contents gets pixelated in
the generated PDF documents. We could use a2x to generate
documents through the DocBook way, but that means dealing with
XSL stylesheets as far as I can tell; that looks time-consuming
and a rather low-priority task. But of course, contributions are
welcome.squeeze, I didn t
notice the 1.9 packages were forked right before that, so were
affected too. I fixed it in sid since then (and in git for
experimental). I noticed that when
Ian reported a crash with large
timeouts in xauth calls, which I couldn t reproduce since
untrusted cookies without XSecurity don t trigger this issue. I
reported that upstream as
FDO#35066,
which got marked as a duplicate of (currently restricted)
FDO#27134. My patch
is currently still waiting for a review.experimental, unless 7.10 migrates to testing first, in
which case that update will target unstable..so symlinks
for a while, and I finally gave it a quick look. It seems one is
supposed to put e.g. libI810XvMC.so.1 in
/etc/X11/XvMCConfig to use that library, so the symlinks are
indeed not needed at all, and I removed them.libxt: to unstable, as mentioned above, with a hot fix,
then with a real fix.synaptics input driver: to unstable and experimental,
fixing the FTBFS on GNU/kFreeBSD.xterm: new upstream, to unstable.libdrm: new upstream, to experimental. A few patches to
hide private symbols were sent upstream, but I ve seen no
reactions yet (and that apparently happened in the past already).xorg-server 1.9.5rc1 then 1.9.5, to unstable.xutils-dev to unstable: the
bootstrap issue goes away,
thanks to Steve s report.libxp to unstable, nothing fancy, that s libxp keyboard input driver: mostly documentation update, to
unstable and experimental.mouse input driver: fixes BSD issues, to unstable and
experimental.intel video driver: to experimental, but the
debian-unstable branch can be used to build the driver against
unstable s server.xfixes: protocol to unstable, and library to experimental
(just in case); this brings support for pointer barriers.openchrome video driver: Julien introduced a debugging
package, and got rid of the (old!) via transitional package. He
also performed his first upload as
a Debian Maintainer. Yay!siliconmotion video driver: to unstable.pixman: new upstream release candidate, to experimentalcompiz packages to experimental. Time for a seventh Debian XSF News issue!
xorg-server 1.10 coming up
(read below), as well as X stack s migration to testing, to
consider before thinking of backporting though.intel cards (see
our FAQ entry). According
to Chris Wilson, current kernels/intel drivers are better for 855+,
but 830/845 still need a miracle.nouveau
driver and the Linux kernel version. As mentioned in
my mail to debian-release@
that would be quite self-contained otherwise. Bottom line: we re
waiting for the kernel.debian-x@,
the plan is to wait for this migration to happen before uploading
new upstream releases of libdrm, the intel driver, and mesa
to unstable. Both libdrm and mesa were prepared for Ubuntu, and
will be likely uploaded to experimental soon. The intel driver
was prepared, but only built against xorg-server 1.10 and
uploaded to experimental for now.xorg-server 1.10 side, the (very late) RandR patches were
proven broken,
so
reverting RandR 1.4
was decided. With some minor tweaks (to the radeon driver), that
went quite well, and xorg-server 1.10 got
released. Unfortunately, there s still some missing fix for the
build system, which explains why I didn t upload a final 1.10 to experimental yet; several
patches were proposed already (I checked a bunch of them), but
we re still
waiting for a final patch.experimental, built against 1.10rc* (see
DXN#6), since I only needed to upload the
following video drivers again: ati, dummy, fbdev, intel,
mach64, nouveau, r128, vesa. It might make sense to add
cirrus to that list next time, for tests under kvm and the like.kbd, mouse, and synaptics, which I uploaded both to
unstable (built against 1.9), and to experimental (built
against 1.10).synaptics device, make sure
you have no configuration issues in xorg.conf; even if that used
to work somehow, autoconfiguration might fail if there s a
misconfigured device (for example, wrong Device option
there). You might want to have a look at our
how to configure input
documentation.1.9/unstable, Tormod Volden prepared
updates for the mga and savage video drivers, which I
sponsored.unstable.Dm-Upload-Allowed field to yes
since he s doing a pretty good job already. It s currently sitting
in NEW accordingly.MultiArch-ify both libx11 and
xorg; both were uploaded.mesa built against wayland libraries (to get the
wayland EGL platform), and the needed mesa bits are (last I
asked) only in master for now.ati and intel video drivers, as
well as on xorg-server again, along with the xorg meta
package. (Clicking on a bug graph below leads to a cached full-year
view.)
| x-x-video-ati | x-x-video-intel | xorg-server | xorg |
|---|---|---|---|
 |
 |
 |
 |
Enough news to release another Debian XSF News issue, after less
than a week.
devd and
came up with a proposal. It s
quite ugly but it looks like it would work with minimal efforts,
and I could then forget about HAL
entirely. Guillem proposed
something more generic/universal, but unfortunately, I have seen no
replies yet.unstable, which comes with plenty of bug fixes, and better
Evergreen support.r600 Gallium in mesa was
a bit premature, so it s going to
be reverted in the next upload.squeeze-candidate but
not squeeze-accepted.unstable, including an important fix to the EXA acceleration
layer, especially fixing a bunch of issues with the radeon
driver. In other news, a big clean-up happened there, making the
good ol build system ( xsfbs ) go away.qxl, I uploaded the sparc drivers (suncg14, suncg3,
suncg6, sunffb, sunleo, suntcx) from a porter box (thanks
to the very responsive DSA team for the quick installation of
needed build dependencies), and Aur lien Jarno kindly uploaded the
newport driver for mips.experimental, but only built a few drivers against it. On the
video side, the API didn t change much, so most drivers build
without modifications: fbdev, then ati, mach64, r128 (ati
depends on the other ones), as well as intel, nouveau, dummy
(useful when there s no monitor connected), and vesa. On the
input side, many changes happened and one needs new upstream
releases, except for the evdev driver (which I uploaded
accordingly). Upstream is currently in the process of releasing
other input drivers, so the following drivers should hit
experimental soon: keyboard/kbd, mouse (both for non-Linux
ports), and synaptics (better than evdev for touchpads).xorg-server s
README.source
mentioning what to keep an eye on when upgrading to a new upstream
release. For example, forgetting a version bump in
xserver-xorg-dev s dependencies could lead to build failures when
xorg-server.pc is used, which is why I uploaded a
new xorg-server revision xorg-announce@.
Next.